A method for collaborative comments or metadata annotation of video

ABSTRACT

A logger or annotator views video in a window or user interface (UI) of a computing device and enters time-stamped metadata or commentary; that metadata or commentary is then automatically displayed on a timeline or other time-based index in a different window or user interface of a second computing device used by a viewer or editor of that video. The metadata or commentary is represented by a marker or icon appearing on a timeline displayed in the window or user interface of a second computing device, and the metadata or commentary is shown when the viewer or editor selects that marker or icon.

BACKGROUND OF THE INVENTION 1. Field of the Invention

This invention relates to a method and system for annotating video. One application is in annotating video for sports video broadcasts in a non-linear editing environment so that an editor can rapidly scan and search the annotated video for specific video frames of relevance.

A portion of the disclosure of this patent document contains material, which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

2. Description of the Prior Art

A ‘metadata annotation system’ allows one or more human or automated users to mark up one or more video frames and associate metadata with those frames external to or inside a non-linear editing environment (NLE) on single or multiple media, such as video from multiple camera angles.

Existing systems allow a user to import those metadata annotations into an NLE via human initiated action. For example, using existing systems, the NLE user must take manual action to choose to import an edit decision list (EDL) file or select, via human initiated action, to import one or more metadata annotations into the NLE.

In contrast this invention provides updates to the NLE in real-time, as close as possible to the live playhead, such that no human initiated action is required by the NLE user to view and work with the metadata annotations in the NLE. Whilst we have described NLE prior art, this invention can be used outside of that context and can be used in many other kinds of applications.

SUMMARY OF THE INVENTION

The invention is a method of annotating video, in which a logger or annotator views that video in a window or UI of a computing device and enters time-stamped metadata or commentary;

-   -   and that metadata or commentary is then automatically displayed         on a timeline or other time-based index in a different window or         UI of a second computing device used by a viewer or editor of         that video.

The method is implemented by a computer processor or processors.

Optional features include any one or more of the following:

-   -   Video is real-time video     -   Video is not raw video but a memory efficient proxy     -   Metadata or commentary is represented by a marker or icon         appearing on the timeline or other time-based index displayed in         the window or UI of the second computing device, and the         metadata or commentary is shown when the viewer or editor         selects that marker or icon or otherwise interact with the         marker or icon to cause the metadata or commentary to be         displayed     -   Window or UI of the second computing device includes a search         function that enables the viewer or editor to search for         specific terms in metadata or commentary     -   Window or UI of the second computing device returns or filters a         list or set of video or clips that each include metadata or         commentary matching a specific search term     -   The viewer or editor can subscribe to or define metadata or         commentary of interest and any video or clips that are annotated         to include the metadata or commentary of interest is then         automatically notified, listed or otherwise provided to the         viewer or editor     -   Automatic display of metadata or commentary in the second         computing device used by the viewer or editor occurs in         real-time and is frame accurate, i.e. identical to the frames         seen by the logger or annotator     -   Metadata or commentary is automatically displayed in the         different window or UI when the logger or annotator makes an         affirmative action, for example selects ‘save’ option or         equivalent or some other button or tile     -   Method is scalable to any number of loggers or annotators and         enables large scale collaboration     -   Method fuses time-stamped metadata or commentary from multiple         different loggers or annotators     -   Editor's window or UI (i.e. the window or UI on the second         computing device) enables rapid definition of clip boundaries,         e.g. in and out points, based on time-stamped metadata or         commentary     -   System automatically generates clip boundaries, e.g. in and out         points, based on time-stamped metadata or commentary     -   Loggers or annotators enter metadata or commentary by selecting         words from a controlled vocabulary displayed on their window or         UI to ensure consistency and eliminate ambiguity     -   Controlled vocabulary is represented by a set of buttons, tiles         or icons, each with a single word or name from the controlled         vocabulary     -   When a logger or annotator selects a word or name on a button or         tile, then that word or name is automatically saved and         displayed on the window or UI of the second computing device     -   Controlled vocabulary is derived from a semantic description or         schema     -   Controlled vocabulary can be fixed or can be dynamically updated     -   Controlled vocabulary is hierarchical and enables searching in         respect of concepts or items at any level of the hierarchy (e.g.         at the top of the hierarchy for football could be ‘goals’, and         one level down could be ‘goals scored from a breakaway’; ‘goals         scored passing defence’; ‘goals scored on the volley’, ‘goals         scored by striker’ etc. so you could search for specific types         of goal, or search more generally for all goals).     -   Controlled vocabulary is mined and managed (e.g. cleansed of         duplicates, simplified to give consistency) automatically     -   Controlled vocabulary is in part derived from or enriched by         social media content     -   Controlled vocabulary includes domain specific data, such as         information on different sports team and players on each team         for a specific game or event captured by the video being         annotated     -   Domain specific data is obtained from several different sources         and aggregated, and the aggregated data is then analysed and         modified to ensure consistency     -   The controlled vocabulary is automatically stamped or identified         with provenance data that includes time, thus allowing reversion         to the precise version of the controlled vocabulary     -   Time stamping a controlled vocabulary, or items within a         controlled vocabulary, enables the annotator etc. to revert to a         required version and also to update or correct any entry     -   Time stamping a controlled vocabulary, or items within a         controlled vocabulary, enables reduced cost of ownership because         it gives a chronological view of the metadata or commentary for         a given asset in the controlled vocabulary     -   The chronological view is mined for interesting graphs of         relationships and analysis, for example statistics—for example,         that this player historically has played for these teams and at         the same time as this player     -   The controlled vocabulary provenance data is included in log         entries such that they can be ranked for accuracy and filtered         or weighted, e.g. this data was from a manual process and has a         weighting of 90% vs. this data was from an automated facial         recognition identifying the player and has a ranking of 60%     -   Method is used to train a machine learning system or classifier     -   Metadata or commentary is generated automatically from sensors         (e.g. sensors that detect passage of race cars; sensors that         detect whether a ball has entered the goal; sensors that detect         whether a tennis ball is in or out of the court; sensors that         detect when a crowd is cheering loudly etc.). Note here that         this is metadata or commentary that is additional to the         metadata or commentary generated by the loggers or annotators.         However, in another aspect of the invention, it is possible that         the metadata or commentary is only or exclusively generated         automatically from sensors.     -   Sensors that enable automatic generation of metadata or         commentary are loT sensors     -   Sensors that enable automatic generation of metadata or         commentary receive a social media feed     -   Sensors that enable automatic generation of metadata or         commentary receive a media data feed that is noisy and the         method includes the step of cleaning that data, including one or         more of filtering, interpretation and substitution of that data,         where substitution includes substituting a word or words for a         single alias     -   The method includes the step of simplifying the data, for         example to remove diacritics such as umlauts and accents to         present a common searchable name tag.     -   A rules engine equipped with the rules for a specific domain         (e.g. tennis, football, basketball etc.) interprets the sensor         data and interprets their output to generate automatically         metadata or commentary that is meaningful in the context of that         domain (e.g. for tennis—‘a 150 mph ace’ could be generated from         the court-side sensors that measure tennis ball speed; ‘ a         double fault’ could be generated from the court-side sensors         that determine if a tennis ball lands within the court; for         football ‘goal!’ could be generated from goal-mouth sensors that         determine if the ball passes the goal posts; for basketball         ‘score!’ % possession′, ‘shot clock start’ etc.)     -   Window or UI of the second computing device is an editing UI         that aggregates all incoming data needed to edit the video     -   Editing UI presents data that has been aggregated at a remote         service     -   Editing UI enables the editor to scroll along a timeline or         other time-based index and to view metadata or commentary         associated with different times along the timeline or time-based         index.     -   The logger or annotator's window or UI includes a window showing         video and also a grid, list or arrangement of buttons, tiles or         icons for the words and/or names in the controlled vocabulary     -   The logger or annotator's window or UI includes tools to enable         the logger or annotator to define in and out points or stop and         start points for a video clip or video section associated with         specific metadata or commentary     -   Editing UI is part of an editing environment or tool such as a         NLE, and the tool automatically generates a highlights reel, or         other sequence or clip or clips of video that has defined         characteristics     -   Video shown in the window or UI is taken from the same camera         that provides the video shown on the second computing device;     -   Video shown in the window or UI is taken from a different camera         from the camera that provides the video shown on the second         computing device. So for example in a security camera system, if         the metadata or commentary (e.g. ‘Intruder alert’) is created in         relation to a video from a camera pointing at a gate, then that         metadata or commentary, or the related marker or icon, could         also appear on a camera feed showing the front door.     -   The video is from one or more cameras filming a sports event     -   The video is from one or more cameras filming a lesson or         educational event     -   The video is from one or more cameras filming a news event     -   The video is from one or more security cameras     -   The video is from one or more courtroom cameras     -   The video is from one or more cameras filing a medical         examination or medical procedure     -   The video is from a video sharing website, such as YouTube.

BRIEF DESCRIPTION OF THE FIGURES

The invention is described using the following Figures:

FIG. 1 is a flow chart depicting the operation of the system.

FIG. 2 is a flow chart depicting the operation of the system in a sports production environment.

FIG. 3 shows the non-linear editing (NLE) UI.

FIG. 4 is a wireframe corresponding to FIG. 3.

FIG. 5 shows the logger's or annotator's UI.

FIG. 6 a wireframe corresponding to FIG. 5.

FIG. 7 shows the logger's or annotator's UI as the logger saves an annotation ‘Pele Pass to Player’ FIG. 8 is a wireframe corresponding to FIG. 7.

FIG. 9 shows the editor's UI immediately before the logger has saved the annotation ‘Pele Pass to Player’.

FIG. 10 shows the editor's UI immediately after the logger has saved the annotation ‘Pele Pass to Player’, showing a new ‘Live Marker’ icon on the timeline associated with that event.

FIG. 11 is a wireframe corresponding to FIG. 10.

FIG. 12 shows how the text of the annotation ‘Pele Pass to Player’ is revealed by the editor hovering his cursor over the Live Marker.

FIG. 13 is a wireframe corresponding to FIG. 12.

FIG. 14 shows the logger's or annotator's UI as the logger saves an annotation ‘Pele Scores a Goal’.

FIG. 15 shows the editor's UI immediately after the logger has saved the annotation ‘Pele Scores a Goal’, showing a new ‘Live Marker’ icon on the timeline associated with that event.

FIG. 16 is a wireframe corresponding to FIG. 15.

FIG. 17 shows the editor's UI as he creates a video clip of Pele scoring a goal.

FIG. 18 is a wireframe corresponding to FIG. 17.

DETAILED DESCRIPTION

One implementation of this invention is a real-time metadata annotation system to provide real-time updates to an editing timeline in a non-linear editing environment (NLE). The system receives input from a collaborative metadata annotation system which allows annotation of single or multiple video frames created against single or multiple live video streams or files. The system produces, as output, one or more annotations on an NLE timeline. Via user configuration, the system can make one or more intermediate calculations on the annotations after creation and before observation by an NLE user. Certain embodiments of the system can use the created annotations to automatically create new video content without the requirement for user input.

FIG. 1 shows a flowchart depicting the operation of the system. As input, the system receives one or more incoming videos files or streams, these are then annotated by one or more human or automated metadata annotators. The system collates these metadata annotations and may optionally perform one or more intermediate calculations based on the metadata annotations. The resulting metadata annotations are automatically added to the NLE timeline requiring no action from the editor to initiate the import of the metadata annotations. Additionally, the system may optionally create one or more video files based on the metadata annotations.

FIG. 2 shows a flowchart depicting the system in use in a sports production environment. For the purpose of this use case description we will assume that the sports event is a basketball game, however, it could equally be any sports, news, reality TV, live stage event or other real-time, fast turn-around production. We will also assume that the output video file is a highlights package for the basketball game.

Firstly, a camera captures footage of the basketball game. This footage is stored in a live growing video file. In this context a live growing video file is one which can be written to by the camera and simultaneously read from by a machine. An example use case for a live growing video file is to allow a number of human operators to watch a basketball game ‘live’ via a web-based video player. For the purpose of this use case we will assume the camera has captured footage of LeBron James scoring a slam dunk.

The live footage from the basketball game is observed by an editor using an NLE and it is simultaneously passed on to a number of human metadata annotators—known colloquially as ‘loggers’—these operators use a computer system to mark up interesting sections of the game such as dunks, blocks and fouls. Metadata is added to these sections to form a metadata annotation, for example, the annotation shown by Table 1. Table 1 describes footage containing a slam dunk by LeBron James between time-codes 00:15:30:12 and 00:15:35:21, this action in the footage is of high quality and has been awarded a 5 star rating by the annotator. Note that the property names (Player, Action) and values (LeBron James, Slam Dunk) are examples of terms derived from a controlled vocabulary.

TABLE 1 Example metadata annotation In Point 00:15:30:12 Out Point 00:15:35:21 Player LeBron James Action Slam Dunk Rating 5 Stars

Once the system receives a metadata annotation it performs a number of intermediate calculations to determine whether the content is of interest to an editor. Each intermediate calculation is configurable, however, for the purpose of this use case we will assume that the system is looking for content rated greater than 4 stars; the slam dunk annotation meets this rating requirement.

As previously identified, an editor is watching the basketball footage live from within an NLE.

Now, the system takes the worthy metadata annotation and automatically adds it to the NLE timeline in the appropriate temporal location. For the annotation to be displayed on the NLE timeline no action is required by the editor, the annotation is automatically added to the timeline by the system.

At this time the editor can see the new slam dunk annotation on the timeline and can choose to include this in the highlights package which he or she is creating. We will assume that the editor chooses to add LeBron James' slam dunk to the highlights package.

Once the editor is satisfied with the highlights package they can choose to export this as a new video file. Having followed this use case the output highlights package will contain a slam dunk from LeBron James.

An additional embodiment includes a user working in the NLE with completed segments of the media. The NLE user is alerted to a new segment arriving in his working folder, often referred to as a bin. In this instance the “loggers” are annotating groups of frames depicting actions that the NLE user has subscribed to. Based on intermediate calculations the specific actions subscribed to by the NLE user are filtered and automatically appended to his bin for consideration on the production timeline, while the live event is still in progress.

FIG. 3-18 depict another use case where the sports event is football.

FIG. 3 shows the NLE screen that the editor uses—this is the window or UI on the second computing device as described in the Summary of the Invention section above. A wire-frame equivalent is shown in FIG. 4. The NLE screen is indicated generally at 1. The NLE user interface includes various windows: the incoming video being reviewed and edited is shown in the left-hand window 2. A timeline 3 sits underneath window 2; the editor can move a control icon to scroll forward and backwards through video shown in the window 2. The output, edited video is shown in window 4. Various lines of control information are included within window 5.

FIG. 5 shows the screen used by remote loggers or annotators. A wire-frame equivalent is shown in FIG. 6. Video is shown in window 6; the logger can move a cursor 7 along time line 3 to select different moments in the video. Control buttons 9 (rewind, stop, play, pause, fast-forward) are under the video window 6, as are ‘in’ and ‘out’ buttons 15, 16 to set the start and end times of a video clip created by the editor. ‘Save& New’, ‘Save’ and ‘New’ buttons 10 are also under the video window 6. To the right of the video window 6 is a grid of buttons 11. Each button is a word from the controlled vocabulary. In this case, the controlled vocabulary panel is divided into a top half, with ‘Action’ words, and a bottom half, with ‘Player’ names. In this example, the Action words are:

-   -   Save, Header, Shot, Miss, Corner, Yellow Card, Goal, Throw in,         Free kick, Pass, Foul, Cross, Penalty, Red card.

The Player names are:

-   -   Beckham, Balotelli, Jeffers, Donovan, Pele, Maradona, Ronaldo         (of course, these names are just illustrative—in reality, they         would be the players actually playing in the game featured in         the video).

By including common actions, all defined by a controlled vocabulary, and selectable by simply selecting the associated button, the workflow or process for generating comments is very fast, especially with a touch screen display. For example, to enter the annotation relating to player Pele passing the ball to another player, the logger just presses the two keys ‘Pele’ then ‘ Pass’. The logger then typically sets the start point for the clip or video segment that should be annotated with “Pele—pass to player” using the start button 15 and endpoint button 16. These start and endpoints are shown on the video timeline with the ‘[’ symbol 13 and the ‘]’ symbol 14. The annotation appears in window 12, as shown in FIG. 7. The corresponding wireframe is FIG. 8, and the text is notionally represented by the ‘XXXXX’ in the comment field 12.

When the user selects the ‘Save+New’ button 10, as shown in FIG. 7 and FIG. 8, then the Pele—pass to player” annotation created by the logger and the related start and end-points for the associated video is automatically passed to the NLE—there is no need for the editor to manually import that annotation or for the annotator to manually export it. So, the editor would be viewing incoming video, as shown in FIG. 9, and then a ‘Live Marker’ symbol 20 appears on the video timeline 3, as shown in FIG. 10, with associated wireframe FIG. 11. If the editor hovers over or selects the ‘Live Marker’ symbol 20, then a window pop-up with the annotation ‘Pele Pass to Player’, as shown in FIG. 12, with associated wireframe FIG. 13. All annotations are searchable by the editor.

With FIG. 14, we return to the logger's screen. Here, Pele has scored a goal and the logger has selected the Action buttons ‘Shot’ and ‘Goal’ and the player button ‘Pele’. The commentary box 12 hence automatically includes the text ‘Pele scores a goal’. Appropriate ‘In’ and ‘Out’ marks are added to the video timeline by the logger. FIG. 15 shows that the editor's NLE screen has been automatically updated with a second ‘Live Marker’ 21 on timeline 3. As the editor hovers over or selects the Live Marker symbol 21, then a window pop-up with the annotation ‘Pele Scores a Goal’, as shown in wireframe version of FIG. 15, namely FIG. 16. The editor can now rapidly create a video clip of just Pele scoring a goal, as shown in FIG. 17, with associated wireframe FIG. 18. The editor defines in and out points defining the clip, 23, and the editor can create and play that clip back in window 4 and rapidly include it in a set of highlight clips.

The same fundamental principles can be used in numerous other contexts.

Additional Use Cases

Security cameras: A security camera feed or feeds could be viewed simultaneously by dozens of different loggers, each able to enter an annotation like ‘intruder’ or ‘front door’ or ‘armed’ or ‘cat’ etc. with different keywords triggering different automated responses (e.g. ‘armed intruder’ could trigger an automated call to the police). By enabling a feed or feed to be watched by many different loggers, possibly in totally different locations, the level of the scrutiny will be much greater than with just a single person viewing the video feed. Also, the annotations can be used to train e.g. a deep learning system since you are providing unambiguous training data the deep learning system can use to associate with specific visual patterns and behaviours.

YouTube: YouTube videos could be annotated by millions of YouTube users, with an aggregator analyzing annotations and filtering the annotations to use only those annotations that are made in excess of a defined threshold. Ordinary users wishing to annotate a YouTube video will call up in their browser the logger tool, complete with controlled vocabulary tiles or buttons that are relevant to the subject of the video. This will enable crowd-sourced analysis and annotation of large numbers of videos and enable content to be searched more effectively (e.g. not just for specific names or titles, but for specific moments within a video).

Courtrooms—e.g. courtroom video is annotated with time-stamped metadata or commentary (e.g. ‘dramatic moment’, ‘judge intervenes’, ‘witness breakdown’ etc.) enabling an editor to rapidly generate an interesting clip or sequence of clips for a news bulletin.

Healthcare—e.g. a specialist physician could be annotating a video interview or examination of or procedure performed on a patient, or a video of a MRI scan. Another physician, perhaps a generalist, could be reviewing the annotated video; annotations could specifically describe clinically important aspects (e.g. a patient is describing their symptoms in a video and the annotator is entering possible diagnoses or other clinically significant comments at the related times in the video, enabling the generalist physician to scroll straight to the clinically important moments).

Monetising legacy video assets—provides a cost-effective way of annotating video since it draws on the power of collaboration—could be possible to crowd-source annotations of for example old newsreels or other types of images for which there are a sufficient number of members of the public willing and competent to annotate these images. This enables a Wikipedia-type crowd-sourced commentary for all video assets. 

1. A method of annotating video in which a logger or annotator views that video in a window or UI of a computing device and enters time-stamped metadata or commentary; and that metadata or commentary is then automatically displayed on a timeline or other time-based index in a different window or user interface (UI) of a second computing device used by a viewer or editor of that video.
 2. The method of claim 1 in which the metadata or commentary is represented by a marker or icon appearing on a timeline displayed in the window or UI of a second computing device, and the metadata or commentary is shown when the viewer or editor selects that marker or icon or otherwise interacts with the marker or icon to cause the metadata or commentary to be displayed.
 3. The method of claim 1 in which the window or UI of the second computing device includes a search function that enables the viewer or editor to search for specific terms in metadata or commentary.
 4. The method of claim 1, in which the window or UI of the second computing device returns or filters a list or set of video or clips that each include metadata or commentary matching a specific search term.
 5. The method of claim 1, in which the viewer or editor can subscribe to or define metadata or commentary of interest and any video or clips that are annotated to include the metadata or commentary of interest is then automatically notified, listed or otherwise provided to the viewer or editor.
 6. The method of claim 1, in which the automatic display of metadata or commentary in the second computing device used by the viewer or editor occurs in real-time and is frame accurate, i.e. identical to the frames seen by the logger or annotator.
 7. The method of claim 1, in which the metadata or commentary is automatically displayed in the different window or UT when the logger or annotator makes an affirmative action, for example selects ‘save’ option or equivalent or some other button or tile.
 8. The method of claim 1, in which the method is scalable to any number of loggers or annotators and enables large scale collaboration.
 9. The method of claim 1, in which the method fuses time-stamped metadata or commentary from multiple different loggers or annotators.
 10. The method of claim 1, in which the video is real-time video, or in which the video is not raw video but a memory efficient proxy.
 11. (canceled)
 12. The method of claim 1, (i) in which the editor's window or UI on the second computing device enables rapid definition of clip boundaries, e.g. in and out points, based on time-stamped metadata or commentary, or (ii) in which an editing application on the second computing device automatically generates clip boundaries, e.g., in and out points, based on time-stamped metadata or commentary.
 13. (canceled)
 14. The method of claim 1, in which the loggers or annotators enter metadata or commentary by selecting words from a controlled vocabulary displayed on their window or UI to ensure consistency and eliminate ambiguity.
 15. The method of claim 14 in which the controlled vocabulary is represented by a set of buttons, tiles or icons, each with a single word or name from the controlled vocabulary.
 16. The method of claim 15 in which (i) when a logger or annotator selects a word or name on a button or tile, then that word or name is automatically saved and displayed on the window or UI of the second computing device; or (ii) in which the controlled vocabulary is derived from a semantic description or schema; or (iii) in which the controlled vocabulary can be fixed or can be dynamically updated; or (iv) in which the controlled vocabulary is hierarchical and enables searching in respect of concepts or items at any level of the hierarchy; or (v) in which the controlled vocabulary is mined and managed automatically; or (vi) in which the controlled vocabulary is in part derived from or enriched by social media content; or (vii) in which the controlled vocabulary includes domain specific data, such as information on different sports team and players on each team for a specific game or event captured by the video being annotated; or (viii) in which the controlled vocabulary is automatically stamped or identified with provenance data that includes time, thus allowing reversion to the precise version of the controlled vocabulary. 17-28. (canceled)
 29. The method of claim 1, when used to train a machine learning system or classifier.
 30. The method of claim 1, in which the metadata or commentary is generated automatically from sensors.
 31. The method of preceding claim 30 in which (i) the sensors that enable automatic generation of metadata or commentary are IoT sensors; or (ii) in which the sensors that enable automatic generation of metadata or commentary receive a social media feed; or (iii) in which the sensors that enable automatic generation of metadata or commentary receive a media data feed that is noisy and the method includes the step of cleaning that data, including one or more of filtering, interpretation and substitution of that data, where substitution includes substituting a word or words for a single alias. 32-33. (canceled)
 34. The method of claim 30, in which the sensors that enable automatic generation of metadata or commentary receive a media data feed that is noisy and the method includes the step of cleaning that data, including one or more of filtering, interpretation and substitution of that data, where substitution includes substituting a word or words for a single alias, and in which the method includes the step of simplifying the data, for example to remove diacritics such as umlauts and accents to present a common searchable name tag.
 35. The method of any claim 30 in which a rules engine equipped with the rules for a specific domain interprets the sensor data and interprets their output to generate automatically metadata or commentary that is meaningful in the context of that domain.
 36. The method of claim 1 in which the window or UI of the second computing device is an editing UI that aggregates all incoming data needed to edit the video.
 37. The method of claim 36 in which (i) the editing UI presents data that has been aggregated at a remote service, or (ii) in which the editing UI enables the editor to scroll along a timeline or other time-based index and to view metadata or commentary associated with different times along the timeline or time-based index, or (iii) in which the logger or annotator's window or UI includes a window showing video and also a grid, list or arrangement of buttons, tiles or icons for the words and/or names in the controlled vocabulary. 38-39. (canceled)
 40. The method of claim 36, in which the logger or annotator's window or UI includes a window showing video and also a grid, list or arrangement of buttons, tiles or icons for the words and/or names in the controlled vocabulary, and in which the logger or annotator's window or UI includes tools to enable the logger or annotator to define in and out points or stop and start points for a video clip or video section associated with specific metadata or commentary.
 41. The method of claim 1, in which the editing UT is part of an editing environment or tool such as a NLE, and the tool automatically generates a highlights reel, or other sequence or clip or clips of video that has defined characteristics.
 42. The method of claim 1, in which the video shown in the window or UI is taken from the same camera that provides the video shown on the second computing device.
 43. The method of claim 1, in which (i) the video shown in the window or UT is taken from a different camera from the camera that provides the video shown on the second computing device; or (ii) in which the video is from one or more cameras filming a sports event or (iii) in which the video is from one or more cameras filming a lesson or educational event; or (iv) in which the video is from one or more cameras filming a news event; or (v) in which the video is from one or more security cameras; or (vi) in which the video is from one or more courtroom cameras; or (vii) in which the video is from one or more cameras filming a medical examination or medical procedure; or (viii) in which the video is from a video sharing website, such as YouTube. 44-50. (canceled) 